Alternative Schema Proposal #1868
Conversation
Re-sync with OpenAPI master
This commit contains the markup for the Alternative Schema Proposal and some supporting documention. A directory structure is proposed so that the supporting data for a proposal is all in the same place.
|
@cmheazel and TSC (@darrelmiller, @earth2marsh, @MikeRalphson, @webron, @whitlockjc ...anyone else?) I've been asked to move the discussion about inline alternative schemas from #1532 to a new issue. I can do that. But we're still somewhere in the process of implementing the new scheme to organize draft proposals and related issues, and I would much prefer to create this new issue within that framework, alongside other issues extracted from that same discussion thread. I think we really need this new process so we can:
I think we are all on board with these goals. Thanks @cmheazel for taking this up. I'd like to help build on this. TSC folks, have you had a chance to review this PR? It would be great to have it soon, especially as we're getting into a higher-intensity review phase on these 3.1 draft proposals. One more thing that would be really helpful: Create a designated GitHub label for each draft proposal. Apply that label to relevant issues and PRs. Specify that label towards the top of the draft proposal, followed by two links:
|
Updated the Alternative Schema proposal to follow the Apple SWIFT pattern.
Additional Cleanup to the Alternative Schema Proposal
|
Updated to use the extension method for the Apple SWIFT-Evolution repository as discussed in the TSC meeting of 4/11/19 |
Moved proposal document up one level. Added numeric pre-fixes to proposal files. Per TSC meeting of April 18, 2019
|
|
||
| |Name |Link |Description | | ||
| |--- | --- | --- | | ||
| |jsonSchema |TBD |JSON Schema | |xsdSchema |TBD |XML Schema | |
|
|
||
| Mixed OAS schema and alternative schema: | ||
|
|
||
| schema: |
There was a problem hiding this comment.
Ah ok so this is actually a thing. This really feels like it’s gonna throw a spanner in the works for inpmenebtors. Why can’t we keep them separate and just have JSON Schema define an array instead of mixing up OpenAPI Schema and other Schema?
This pull request proposes a directory structure for documenting enhancements to the OpenAPI specification. It is also populated with the markdown and supporting information for the Alternative Schema proposal.